River: an intermediate language for stream processing
نویسندگان
چکیده
منابع مشابه
River: an intermediate language for stream processing
This paper presents both a calculus for stream processing, named Brooklet, and its realization as an intermediate language, named River. Because River is based on Brooklet, it has a formal semantics that enables reasoning about the correctness of source translations and optimizations. River builds on Brooklet by addressing the real-world details that the calculus elides. We evaluated our system...
متن کاملStream Processing on the Grid: an Array Stream Transforming Language
Specific requirements of stream processing on the Grid are discussed. We argue that when the stream processing paradigm is used for cluster computing, the processing components can be coded in the form of data-parallel recurrence relations with stream synchronization and filtering at the interfaces. We propose a programming language ASTL in which such components can be written and describe some...
متن کاملLanguage design for distributed stream processing
Applications that combine live data streams with embedded, parallel, and distributed processing are becoming more commonplace. WaveScript is a domain-specific language that brings high-level, type-safe, garbage-collected programming to these domains. This is made possible by three primary implementation techniques, each of which leverages characteristics of the streaming domain. First, WaveScri...
متن کاملS-Net: A Typed Stream Processing Language
We propose a view on a data-processing application as a typed streaming network. The arcs of the network represent recordvalued data streams and the nodes encapsulate recurrence relations on them. We propose a type system in which both the arcs and the nodes are statically subtyped, with the overall subtyping consistency of the network assured by type reconciliation algorithms. The proposed typ...
متن کاملStream Processing Hardware from Functional Language Specifications
We describe work-in-progress which aims at compiling suitably restricted functional programs with lazy lists directly into hardware. This extends previous work on SAFL which demonstrated that functional languages are effective at describing “fire-and-wait-for-result” programs, but for which stream-like I/O was awkward or impossible. Other frameworks (e.g. Lava) have used functional languages as...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Software: Practice and Experience
سال: 2015
ISSN: 0038-0644
DOI: 10.1002/spe.2338